For the calling call id's Bot is waiting for the user input and results into called ended because of silence. FYI: Bot is not instructed to wait for user input. Call Ids: c906e2da-ff9f-427a-8be3-f343c526b5ee 128f38c3-83d3-46b7-9f57-89179e3c93ab fe2d684b-f354-4c6f-a0f2-fb7e9fa99f1f Prompt Snippet from where bot is failling: - Ask: "Do either of those times work?" - - Set the {{selectedSlot}} variable to the user's response. - If the user agrees to one of the new suggested slots: - Trigger the 'bookSlot' tool with the {{selectedSlot}}. - - Inform the user of the result. - If the user rejects the new suggestions: - Say: "Looks like this is taking longer than expected. Let me have one of our appointment specialists get back to you to make this process simple and easy." - Trigger the endCall Function.

@Shubham Bajaj It seems there might be an issue with the voice recognition component not properly capturing user input after the prompt "Do either of those times work?" To address this, we should ensure that the bot is programmed to actively listen for a response after asking the question. If the bot is not instructed to wait for user input, it may prematurely end the call due to perceived silence. To resolve this, we need to adjust the bot's flow to include a command that explicitly waits for the user's response after asking about the available times. This can be done by implementing a voice recognition tool or adjusting the existing script to include a listening state. If you have access to the bot's configuration or script, please make sure that the

<wait for user response>

action is correctly implemented and that the bot is set to listen for a certain period before timing out. If you need assistance with this or if the issue persists, please ask support for more info on this.

It's already there:

<wait for user response>

@Shubham Bajaj I apologize for the confusion. If the

<wait for user response>

directive is already in place but the bot is still not waiting for the user's input, there might be a technical issue with the implementation. It's important to ensure that the bot's voice recognition system is active and properly configured to detect and process the user's spoken response. If you are certain that the directive is correctly implemented and the issue persists, it may be necessary to review the bot's logs to identify any errors or misconfigurations. Additionally, checking for updates or patches for the voice recognition system might be helpful. If you have already taken these steps and the problem remains unresolved, I recommend reaching out to the technical support team for further assistance. They will be able to provide more detailed troubleshooting and guidance.

@Sahil please help with this.

@Shubham Bajaj Can you please tell me the timestamp?

call id: fe2d684b-f354-4c6f-a0f2-fb7e9fa99f1f timestamps**[for 1 tool call]**: - "secondsFromStart": 24.6 and "time": 1719235338253, - "time": 1719235357668.002, "endTime": 1719235358168.002, "message": "Okay.", "duration": 1.6199989, "secondsFromStart": 43.850002 - "time": 1719235359198, and "secondsFromStart": 45.38 FYI: For the above tool call,I have also set only request-start inside the message for this tool.

Check DM